Data Groups
With few exceptions, data groups must be defined in a device template file (DTF) in order for them to be available for use on a remote device. Which data groups are defined by a device template file depends on protocol, device type, and unique configuration.
CygNet distributes sample device template files for its EIEs, each of which typically serves one or more hardware models along with applicable firmware. Therefore, the data groups described below are only those data groups defined by CygNet in sample device template file(s). Your template(s) might not include some of the data groups described below. Device template files exist to enable users to customize device configurations; however, CygNet is not responsible for changes made by users.
For information about data group definitions and device template files, see Device Template Files.
For more information about data group dependencies, see Data Group Dependencies.
Note:
-
When point processing is performed on history data groups, only closed records will be published and processed to points. If a device has leading timestamped records and returns the current, open record, point processing will not be performed for that record, even though there is data in the DDS transaction. The point record will be updated only when that record is closed. This is to avoid a situation where a point has multiple entries with the same timestamp, since an open record may be still updating values with each new poll, but each update will have the same timestamp. For example, say you start polling for a daily history record at 8:00am, you’ll get the first value at 8:00am, then if you poll every five minutes, you’ll get new values throughout the day at the exact same timestamp. A history record is basically an array of data with a timestamp and values where the values have different process variables for each incremental poll. The timestamp won’t get written until the record is closed, which happens at the end of the time period, in this case, a day.
Lufkin MPC/RPC EIE Data Groups
| Data Group Type | Usage Notes |
|---|---|
|
AI24 |
"Analog Input 24-Hour Trend" |
|
AI60 |
"Analog Input 60-Day Trend" |
|
AnalogCfg |
"Analog Configuration" |
|
AnlgData |
"Analog Data" |
|
"Command Message" |
|
|
Composite Data Group |
The "Composite Data Group" is a special kind of data group that enables you to combine any data group element(s) from any data group(s) as long as they are in the same template as the composite data group. The "Composite Data Group" does not appear in a remote device editor unless it has been defined in the relevant device template file. See Composite Data Group. |
|
DateTime |
"Date and Time" |
|
DownCfg |
"Downhole Configuration" |
|
The "Dynagraph Card" data group references a specific subset of support data groups and elements. These items are required to support a connected system; they are not required if you are not reliant on a connected system for functionality or data. |
|
|
DynaConfig |
"Pumpoff Configuration" |
|
MinLoad60 |
"Min Load 60-Day Trend" |
|
PeakLoad60 |
"Peak Load 60-Day Trend" |
|
Prod60 |
"Inferred Production History" |
|
ProgData |
"Program Data" |
|
Runtime24 |
"Runtime 24-Hour Trend" |
|
Runtime60 |
"Runtime 60-Day Trend" |
|
SampMod |
"Sample templated modbus" |
|
StatusData |
"Status Data" |
|
WellConfig |
"Well Configuration" |

